Autonomous vehicle fueling with centralized scheduling

ABSTRACT

Vehicles can be equipped to operate in both autonomous and occupant piloted mode. Refueling stations can be equipped to refuel autonomous vehicles without occupant assistance. Refueling stations can be equipped with a fueling control computer that communicates with vehicles via wireless networks to move vehicles between waiting zones, service zones and served zones. Refueling stations can include liquid fuel, compressed gas and electric charging.

BACKGROUND

Vehicles can be equipped to operate in both autonomous and occupantpiloted mode. Refueling stations can be equipped to refuel autonomousvehicles without occupant assistance and can include liquid fuel,compressed gas and electric charging.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a vehicle in accordance with disclosed examples;

FIG. 2 is a diagram of a refueling station in accordance with disclosedexamples;

FIG. 3 is a diagram of a refueling station in accordance with disclosedexamples;

FIG. 4 is a flowchart diagram of a process to move vehicles to fuelingzones based on control signals in accordance with disclosed examples;and

FIG. 5 is a flowchart diagram of a process to determine and transmitcontrol signals for multiple vehicles in accordance with disclosedexamples.

DETAILED DESCRIPTION

Vehicles can be equipped to operate in both autonomous and occupantpiloted mode. By a semi- or fully-autonomous mode, defined more fullybelow we mean in short a mode of operation wherein a vehicle can bepiloted by a computing device as part of a vehicle information systemhaving sensors and controllers. The vehicle can be occupied orunoccupied, but in either case the vehicle can be piloted withoutassistance of an occupant. Vehicles can be powered by a variety of fueltypes, including liquid petroleum- or alcohol-based fuels, compressedgases such as liquefied petroleum or hydrogen, or electricity. For allfuel types, vehicles can be equipped to be refueled at refuelingstations.

Refueling stations can be equipped to provide a variety of refuelingoptions including automated and manual fueling, fuel type and fillertype/location. Fuels can include liquid petroleum or alcohol fuels,compressed gases or electric charging. Fueling can be fully automated,requiring the vehicle to be in autonomous mode and operable to respondto commands from a fuel pump, or fueling can be manual, requiring someassistance of an attendant or occupant to complete. Vehicles can requirerefueling while in autonomous mode. Vehicles in autonomous mode can beprogrammed to locate refueling stations.

Equipping vehicles with wireless networks operative to communicate withother vehicles and fueling control computers associated with refuelingstations can permit one or more vehicles in autonomous mode to refuel atthe refueling station. In cases where vehicles include occupants, one ormore occupant preferences can be communicated to the fueling controlcomputer and other vehicles. Wireless networks can include cellulartelephone networks, Wi-Fi, and dedicated short range communications(DSRC) technology including Bluetooth Low Energy (BLE) or other wirelesstechnologies, for example. Fueling control computer can direct one ormore vehicles via wireless networks to refuel the vehicles efficientlywhile satisfying occupant preferences.

FIG. 1 is a diagram of a vehicle information system 100 that includes avehicle 110 operable in autonomous (“autonomous” by itself in thisdisclosure means “fully autonomous”) and occupant piloted (also referredto as non-autonomous) mode in accordance with disclosed implementations.Vehicle 110 also includes one or more computing devices 115 forperforming computations for piloting the vehicle 110 during autonomousoperation. Computing devices 115 can receive information regarding theoperation of the vehicle from sensors 116.

The computing device 115 includes a processor and a memory such as areknown. Further, the memory includes one or more forms ofcomputer-readable media, and stores instructions executable by theprocessor for performing various operations, including as disclosedherein. For example, the computing device 115 may include programming tooperate one or more of vehicle brakes, propulsion (e.g., control ofacceleration in the vehicle 110 by controlling one or more of aninternal combustion engine, electric motor, hybrid engine, etc.),steering, climate control, interior and/or exterior lights, etc., aswell as to determine whether and when the computing device 115, asopposed to a human operator, is to control such operations.

The computing device 115 may include or be communicatively coupled to,e.g., via a vehicle communications bus as described further below, morethan one computing devices, e.g., controllers or the like included inthe vehicle 110 for monitoring and/or controlling various vehiclecomponents, e.g., a powertrain controller 112, a brake controller 113, asteering controller 114, etc. The computing device 115 is generallyarranged for communications on a vehicle communication network such as abus in the vehicle 110 such as a controller area network (CAN) or thelike; the vehicle 110 network can include wired or wirelesscommunication mechanism such as are known, e.g., Ethernet or othercommunication protocols.

Via the vehicle network, the computing device 115 may transmit messagesto various devices in the vehicle and/or receive messages from thevarious devices, e.g., controllers, actuators, sensors, etc., includingsensors 116. Alternatively, or additionally, in cases where thecomputing device 115 actually comprises multiple devices, the vehiclecommunication network may be used for communications between devicesrepresented as the computing device 115 in this disclosure. Further, asmentioned below, various controllers or sensing elements may providedata to the computing device 115 via the vehicle communication network.

In addition, the computing device 115 may be configured forcommunicating through a vehicle-to-infrastructure (V-to-I) interface 111with a remote server computer 120, e.g., a cloud server, via a network130, which, as described below, may utilize various wired and/orwireless networking technologies, e.g., cellular, BLUETOOTH® and wiredand/or wireless packet networks. The computing device 115 also includesnonvolatile memory such as are known. Computing device can loginformation by storing the information in nonvolatile memory for laterretrieval and transmittal via the vehicle communication network andV-to-I interface 111 to a server computer 120 or user mobile device 160.

As already mentioned, generally included in instructions stored in thememory and executed by the processor of the computing device 115 isprogramming for operating one or more vehicle 110 components, e.g.,braking, steering, propulsion, etc., without intervention of a humanoperator. Using data received in the computing device 115, e.g., thesensor data from the sensors 116, the server computer 120, etc., thecomputing device 115 may make various determinations and/or controlvarious vehicle 110 components and/or operations without a driver tooperate the vehicle 110. For example, the computing device 115 mayinclude programming to regulate vehicle 110 operational behaviors suchas speed, acceleration, deceleration, steering, etc., as well astactical behaviors such as a distance between vehicles and/or amount oftime between vehicles, lane-change minimum gap between vehicles,left-turn-across-path minimum, time-to-arrival at a particular locationand intersection (without signal) minimum time-to-arrival to cross theintersection.

Controllers, as that term is used herein, include computing devices thattypically are programmed to control a specific vehicle subsystem.Examples include a powertrain controller 112, a brake controller 113,and a steering controller 114. A controller may be an electronic controlunit (ECU) such as is known, possibly including additional programmingas described herein. The controllers may communicatively be connected toand receive instructions from the computing device 115 to actuate thesubsystem according to the instructions. For example, the brakecontroller 113 may receive instructions from the computing device 115 tooperate the brakes of the vehicle 110.

The one or more controllers 112, 113, 114 for the vehicle 110 mayinclude known electronic control units (ECUs) or the like including, asnon-limiting examples, one or more powertrain controllers 112, one ormore brake controllers 113 and one or more steering controllers 114.Each of the controllers 112, 113, 114 may include respective processorsand memories and one or more actuators. The controllers 112, 113, 114may be programmed and connected to a vehicle 110 communications bus,such as a controller area network (CAN) bus or local interconnectnetwork (LIN) bus, to receive instructions from the computing device 115and control actuators based on the instructions.

Sensors 116 may include a variety of devices known to provide data viathe vehicle communications bus. For example, a radar fixed to a frontbumper (not shown) of the vehicle 110 may provide a distance from thevehicle 110 to a next vehicle in front of the vehicle 110, or a globalpositioning system (GPS) sensor disposed in the vehicle 110 may providea geographical coordinates of the vehicle 110. The distance provided bythe radar or the geographical coordinates provided by the GPS sensor maybe used by the computing device 115 to operate the vehicle 110autonomously or semi-autonomously.

The vehicle 110 is generally a land-based vehicle 110 operable inautonomous and occupant piloted mode having three or more wheels, e.g.,a passenger car, light truck, etc. The vehicle 110 includes one or moresensors 116, the V-to-I interface 111, the computing device 115 and oneor more controllers 112, 113, 114.

The sensors 116 may be programmed to collect data related to the vehicle110 and the environment in which the vehicle 110 is operating. By way ofexample, and not limitation, sensors 116 may include, e.g., altimeters,cameras, LiDAR, radar, ultrasonic sensors, infrared sensors, pressuresensors, accelerometers, gyroscopes, temperature sensors, pressuresensors, hall sensors, optical sensors, voltage sensors, currentsensors, mechanical sensors such as switches, etc. The sensors 116 maybe used to sense the environment in which the vehicle 110 is operatingsuch as weather conditions, the grade of a road, the location of a roador locations of neighboring vehicles 110. The sensors 116 may further beused to collect dynamic vehicle 110 data related to operations of thevehicle 110 such as velocity, yaw rate, steering angle, engine speed,brake pressure, oil pressure, the power level applied to controllers112, 113, 114 in the vehicle 110, connectivity between components andelectrical and logical health of the vehicle 110.

FIG. 4 is a flowchart diagram of a process 400 for refueling vehicles110 in autonomous operation described in relation to FIGS. 2 and 3.Process 400 can be implemented on computing device 115, inputtinginformation from sensors 116, executing instructions and sending controlsignals via controllers 112, 113, 114, for example. Process 400 includesmultiple steps taken in the disclosed order. Process 400 also includesimplementations including fewer steps or can include the steps taken indifferent orders.

Process 400 begins at step 402, where computing device 115 according tothe process 400 transmits one or more fueling request signals to afueling control computer 202 at a refueling station 200 as illustratedin FIG. 2, where arriving vehicle 204 can transmit one or more fuelingrequest signals to a fueling control computer 202. Arriving vehicle canestablish short range communications with fueling control computer 202via wireless networking, including cellular telephone networks and Wi-Fivia V-to-I interface 111, and dedicated short range communications(DSRC) technology, for example Bluetooth low energy (BLE) (seewww.bluetooth.com, Bluetooth SIG, Inc., Aug. 8, 2016), for example, tocommunicate with fueling control computer 202 having similar networkingcapability.

An arriving vehicle 204, whether autonomous, semi-autonomous, oroccupant piloted, can establish short range communications with fuelingcontrol computer 202 and transmit fueling request signals that informthe fueling control computer 202 of the type and amount of fuelrequested and the operating characteristics of fueling such as locationof fuel input and refueling technique, including automatic or manual.

At step 404 Fueling control computer 202 can receive the fueling requestsignals and determine fueling control signals including instructions tomove to one or more waiting zones 206, one or more service zones 210 orone or more served zones 208 and transmit the fueling control signals toarriving vehicle 204. The fueling control signals can includeinstructions to move to one or more waiting zones 206, one or moreservice zones 210. Once an arriving vehicle 204 is refueled, fuelingcontrol signals can include instructions to move to or one or moreserved zones 208.

Fueling control computer 202 can require, for example, that all arrivingvehicles 204 be wirelessly networked and capable of autonomousoperation. In this case, fueling control signals can includeinstructions to the computing device 115 to move the vehicle to theindicated zones autonomously. In this manner, arriving vehicles 204could be queued up in waiting zones 206 to access fuel pumps 212 inservice zones 210, and then moved to served zones 208.

This progression is shown in FIG. 3, where arriving vehicle 304transmits fueling request signals to fueling control computer 302 at arefueling station 300 via wireless networking. Fueling control computer302 receives fueling request signals from arriving vehicle 304 andprocesses them to determine fueling control signals to transmit toarriving vehicle 304.

Arriving vehicle 304 can also communicate wirelessly with vehicles 304,308, 318, 320, which can be included in waiting zones 306, service zones310, served zones 316 or amenities 326 to coordinate movement ofarriving vehicle 304 such as queueing in service zones 310 and parkingat amenities 326 with vehicles 304, 308, 318, 320, 328, for example.

Fueling control computer 302 has transmitted fueling control signalswirelessly to move waiting vehicles 308 to waiting zones 306, fuelingvehicles 318 to fueling stations 312 at service zones 310 or servedvehicles 318 to served zones 316 following refueling. Fueling computercan determine how to move vehicles in order to reduce waiting time forthe most vehicles, or other algorithms designed to improve efficiency ofservice delivery.

Returning to FIG. 4, at step 406 the one or more vehicles 304, 308, 318,320, 328 receiving fueling control signals from fueling control computer302 move to or from the appropriate fueling zones, including waitingzones 306, service zones 310 or served zones 316. The vehicles 304, 308,318, 320 328 in autonomous mode and programmed to follow instructionsincluded in fueling control signals transmitted by fueling controlcomputer 302. Fueling request signals and fueling control signals caninclude financial information related to refueling, so that payment canbe made as the fuel is dispensed.

Once refueling is complete, fueling control computer 302 can transmitfueling control signals to one or more vehicles 304, 308, 318, 320, 328to either join served vehicles 320 at served zones 316 or depart therefueling station 300, as shown by departing vehicle 324.

In one example, vehicles that are not capable of autonomous operationcould be accommodated by fueling control computers 302 if the vehiclecould transmit and receive the appropriate signals via wireless networkand translate the fueling controls signals into human language, such as“GO TO PUMP 8, PARK WITHIN YELLOW LINES AND OPEN FUEL DOOR”, forexample. If the occupant pilots the vehicle appropriately and concludesthe financial aspects of refueling via wireless network, refueling couldbe achieved without autonomous control.

At some refueling stations 200, 300, for safety and efficiency,autonomous control of arriving vehicles 204, 304 can be required. Sincearriving vehicles 204, 304 can be occupied, and since occupants can havepreferences regarding refueling and amenities 214, 326, occupantpreferences can be included in fueling request signals. Occupantpreferences can include requests to visit amenities 214, 326 in additionto refueling. Amenities 214, 326 include restrooms, restaurants, shops,picnic, pet areas and parking for example. Parking can includehandicapped, short-term and rest areas and drop off and pickup areas.Waiting zones 206, 306 can also include parking, for example.

In one example, arriving vehicle 304 can transmit fueling requestsignals to fueling control computer 302 indicating that arriving vehiclerequests a certain amount of a certain type fuel, and has a fuelingsystem with certain operating characteristics. Fueling request signalscan include occupant preferences including a request to visit amenities326 to use a restroom, for example. Fueling control computer 302 canreceive and process fueling request signals from arriving vehicle 304along with fueling request signals from other vehicles 308, 318, 320,328 and determine fueling control signals to transmit to arrivingvehicle 304.

The fueling control signals can include instructions to arriving vehicle304 to move to a parking space at amenities 326 near a restroom, forexample. Occupant preferences can include requests for amenities 326such as handicapped parking or nearby parking due to inclement weather.Fueling control computer 302 can receive these fueling request signalsand transmit fueling control signals that satisfy the occupant'spreferences by including instructions to move arriving vehicle to theappropriate amenities 326 or waiting, service or served zones 306, 310,316.

Once the arriving vehicle 304 is parked at the amenities 326, occupantcan exit the arriving vehicle 304 to visit the restroom, for example.Arriving vehicle 304 can transmit a fueling request signal to thefueling control computer 302 indicating the occupant's exit. Fuelingcontrol computer 302 can transmit fueling control signals to arrivingvehicle 304 instructing arriving vehicle 304 to move to a service zone310 for refueling.

Since fueling control computer can recall that an occupant associatedwith arriving vehicle 304 exited the arriving vehicle 304 to visitamenities 326, when refueling is complete for arriving vehicle 304,fueling control computer 302 can send fueling control signals toarriving vehicle 304 including instructions to move to served zones 316to join served vehicles 320. Fueling control signals can instruct thearriving vehicle 304 to move to a served zone 316 near the amenities326. In this manner, the arriving vehicle 304 can be positioned so thatthe occupant can conveniently reoccupy the arriving vehicle 304 anddepart the refueling station, as shown by departing vehicle 324.

In this manner, the arriving vehicle 304 can be refueled as soon as theappropriate fueling station 312 is available, thereby optimizingutilization of fueling stations 312 associated with service zones 310and minimizing a wait for refueling while satisfying occupantpreferences associated with refueling station 300 amenities 326. Inother cases, where arriving vehicle 304 can be unoccupied or whereoccupant stays in the arriving vehicle, once refueling is completearriving vehicle 304 can depart, as shown by departing vehicle 324.

In summary, FIG. 4 illustrates a process 400 for fueling autonomousvehicles with centralized scheduling by transmitting fueling requestsignals from vehicles 304, 308, 318, 320, 328 to a fueling controlcomputer 302, transmitting fueling control signals from fueling controlcomputer 302 to vehicles 304, 308, 318, 320, 328, and moving vehicles304, 308, 318, 320, 324 to one or more zones 306, 310, 316 or amenities326 based on instructions from fueling control computer 302.

Computing devices 115 associated with arriving vehicle 304 can repeatprocess 400 multiple times at refueling station 300 respectively inorder to refuel arriving vehicles 304 while satisfying occupantpreferences. For example, arriving vehicles 304 can move amenities 326,drop off occupant then repeat process 400 and move to a waiting zone306. When a fueling station 312 becomes available, steps 404 and 406 ofprocess 400 can be repeated to move arriving vehicles 304 to one or morefueling stations 312.

When fueling is complete, steps 404 and 406 of process 400 can berepeated to move vehicle 304 to serve zones 316 to join served vehicles320 to wait for occupant to return from amenities, 326 for example, ordepart, as shown by departing vehicle 324. Computing devices associatedwith fueling control computer 302 can also transmit messages viawireless networks to mobile devices such as cell phones to alertoccupant that refueling is complete and arriving vehicle 304 is movingto served zone 316.

FIG. 5 is a flowchart diagram of an example process 500 for centralizedscheduling of vehicle 110 refueling for vehicles 110 in autonomousoperation described in relation to FIGS. 2 and 3. Process 500 can beimplemented on a computing device including a processor and nonvolatilememories such as are known associated with fueling control computer 202,302, wirelessly networked to vehicles 304, 308, 318, 320, 324 asdescribed above. Process 500 includes multiple steps taken in thedisclosed order. Process 500 also includes implementations includingfewer steps or can include the steps taken in different orders.

Process 500 begins at step 502, where fueling control computer 302receives fueling request signals from vehicles 304, 308, 318, 320, 328via wireless network. Request signals can include fueling requestinformation and occupant preference information. At step 504 fuelingcontrol computer 302 determines control signals including instructionsto move to certain zones 306, 310, 316 for the vehicles 304, 308, 318,320, 328.

The control signals can be determined based on probability theoryregarding servicing clients arriving at random intervals to minimizewait times, constrained by the occupant requests, for example. Largenumbers of requests and limited resources can mandate queuing. Fuelingcontrol computer can manage queues for service zones 310 and foramenities 326 associated with refueling station 300, for example.Service at a service zone can include refueling at a fueling station 312and amenities 326 can include restrooms, restaurants, shops, picnic, petareas and parking for example. Parking can include handicapped,short-term and rest areas and drop off and pickup areas.

Vehicles 308 in waiting zones 306 can be in queues waiting for parkingor service, for example. Queues can be managed on a first-in, first-outbasis. Single queues for multiple identical resources can be implementedto minimize average wait times, for example. Queues can changedynamically as vehicles 304, 308, 318, 320, 328 enter and exit refuelingstation 300 and transmit new fueling request signals to fueling controlcomputer 302. This can require transmitting new fueling control signalsto vehicles 304, 308, 318, 320, 328.

At step 506 the fueling control computer 302 transmits the fuelingcontrol signals to the vehicles 304, 308, 318, 320, 328 via wirelessnetwork. The fueling control signals include instructions to move one ormore of vehicles 304, 308, 318, 320, 328 to one or more of zones 306,310, 316 so as to optimize refueling while satisfying occupantpreferences. Fueling control computer 302 can monitor vehicles 304, 308,318, 320, 324 via wireless network to determine compliance with thetransmitted instructions, for example. Other techniques for monitoringcompliance with transmitted instructions include video or other sensors,for example.

In summary, FIG. 5 is a process 500 for centralized scheduling ofautonomous vehicle scheduling by a fueling control computer 302operative to receive fueling request signals from vehicles 304, 308,318, 320, 328, optimally schedule refueling while satisfying occupantpreferences by transmitting fueling control signals to vehicles 304,308, 318, 320, 328 instructing them to move to zones 306, 310, 316 andamenities 326.

Computing devices such as those discussed herein generally each includeinstructions executable by one or more computing devices such as thoseidentified above, and for carrying out blocks or steps of processesdescribed above. For example, process blocks discussed above may beembodied as computer-executable instructions.

Computer-executable instructions may be compiled or interpreted fromcomputer programs created using a variety of programming languagesand/or technologies, including, without limitation, and either alone orin combination, Java™, C, C++, Visual Basic, Java Script, Perl, HTML,etc. In general, a processor (e.g., a microprocessor) receivesinstructions, e.g., from a memory, a computer-readable medium, etc., andexecutes these instructions, thereby performing one or more processes,including one or more of the processes described herein. Suchinstructions and other data may be stored in files and transmitted usinga variety of computer-readable media. A file in a computing device isgenerally a collection of data stored on a computer readable medium,such as a storage medium, a random access memory, etc.

A computer-readable medium includes any medium that participates inproviding data (e.g., instructions), which may be read by a computer.Such a medium may take many forms, including, but not limited to,non-volatile media, volatile media, etc. Non-volatile media include, forexample, optical or magnetic disks and other persistent memory. Volatilemedia include dynamic random access memory (DRAM), which typicallyconstitutes a main memory. Common forms of computer-readable mediainclude, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, any other magnetic medium, a CD-ROM, DVD, any otheroptical medium, punch cards, paper tape, any other physical medium withpatterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any othermemory chip or cartridge, or any other medium from which a computer canread.

All terms used in the claims are intended to be given their plain andordinary meanings as understood by those skilled in the art unless anexplicit indication to the contrary in made herein. In particular, useof the singular articles such as “a,” “the,” “said,” etc. should be readto recite one or more of the indicated elements unless a claim recitesan explicit limitation to the contrary.

The term “exemplary” is used herein in the sense of signifying anexample, e.g., a reference to an “exemplary widget” should be read assimply referring to an example of a widget.

The adverb “approximately” modifying a value or result means that ashape, structure, measurement, value, determination, calculation, etc.may deviate from an exact described geometry, distance, measurement,value, determination, calculation, etc., because of imperfections inmaterials, machining, manufacturing, sensor measurements, computations,processing time, communications time, etc.

In the drawings, the same reference numbers indicate the same elements.Further, some or all of these elements could be changed. With regard tothe media, processes, systems, methods, etc. described herein, it shouldbe understood that, although the steps of such processes, etc. have beendescribed as occurring according to a certain ordered sequence, suchprocesses could be practiced with the described steps performed in anorder other than the order described herein. It further should beunderstood that certain steps could be performed simultaneously, thatother steps could be added, or that certain steps described herein couldbe omitted. In other words, the descriptions of processes herein areprovided for the purpose of illustrating certain embodiments, and shouldin no way be construed so as to limit the claimed invention.

We claim:
 1. A method, comprising: transmitting one or more fuelingrequest signals to a fueling control computer; receiving one or morecontrol signals from a fueling control computer; and moving to one ormore fueling zones in response to the control signals.
 2. The method ofclaim 1 wherein fueling request signals include occupant preferences andfuel type.
 3. The method of claim 2 wherein the fueling control computerdetermines the control signals based on fueling request signals.
 4. Themethod of claim 3 wherein the fueling control computer determinescontrol signals based on fueling request signals for a plurality offueling vehicles.
 5. The method of claim 4 wherein the fueling controlcomputer determines control signals based on minimizing fueling timesfor the plurality of fueling vehicles in first in/first service orderprocessing while meeting occupant preferences.
 6. The method of claim 1wherein moving to one or more fueling zones includes moving to one ormore waiting zones, one or more service zones and one or more servedzones.
 7. The method of claim 1 wherein the control signals aretransmitted and received via a wireless network.
 8. The method of claim1 wherein moving to one or more zones in response to the control signalsis performed by an occupant.
 9. The method of claim 1 wherein moving toone or more zones in response to the control signals is performed by anautonomous vehicle.
 10. An apparatus, comprising: a processor; and amemory, the memory storing instructions executable by the processor to:transmit one or more fueling request signals to a fueling controlcomputer; receive one or more control signals from a fueling controlcomputer; and move to one or more fueling zones in response to thecontrol signals.
 11. The apparatus of claim 10 wherein the fuelingrequest signals include occupant preferences and fuel type.
 12. Theapparatus of claim 10 wherein moving to one or more fueling zonesincludes moving to one or more waiting zones, one or more service zonesand one or more served zones.
 13. The apparatus of claim 10 furthercomprising instructions to: transmit and receive the control signals viaa wireless network.
 14. The apparatus of claim 10 wherein moving to oneor more zones in response to the control signals is performed by anoccupant.
 15. The apparatus of claim 10 wherein moving to one or morezones in response to the control signals is performed by an autonomousvehicle.
 16. A fueling control computer, comprising: a processor; amemory, the memory storing instructions executable by the processor to:receive fueling request signals from one or more vehicles; receivestatus signals from one or more service zones; and command the one ormore vehicles to move to one or more respective zones by transmittingcontrol signals based on fueling request signals and the status signals.17. The fueling control computer of claim 16 further comprisinginstructions to: receive fueling request signals including fuel type andoccupant preferences.
 18. The fueling control computer of claim 16further comprising instructions to: determine the control signals basedon the fueling request signals.
 19. The fueling control computer ofclaim 18 further comprising instructions to: determine control signalsbased on fueling request signals for a plurality of fueling vehicles.20. The fueling control computer of claim 19 further comprisinginstructions to: determine control signals based on minimizing fuelingtimes for the plurality of fueling vehicles in first in/first serviceorder processing while meeting occupant preferences.